What was New in the Fragmalyzer 1.1

What was new in version 1.1

Save as Stub version 1.1 plug-in included
PowerPC Code Browser version 1.0 plug-in included
Script menu support! Sample AppleScripts included.
Browser windows are now Theme-savvy
Extended keyboard-equivalents are supported under the new Menu Manager (OS 8.5).
File/Open (via Nav Services) now displays every file that has a PEF (not just those with a 'cfrg' resource)
Faster lists now support type-selection
Splash no longer shows every time the Fragmalyzer is launched
Enhanced plug-in API
Fragments in "safe" resources are now scanned (see MixedMode.r template)
Accelerated, fat, and safe resources are identified as such in information display
Support for site/worldwide license files (serial numbers need not be entered!)
More scripting changes:

properties of application:

preferred web browser: returns user's preferred web browser (name and signature)
TCP will dial: accessing the Internet will cause the modem to start dialing

properties of fragments:

build date: was string, now is a date ('ldt '). NT dates are automatically converted to Mac OS dates.
container: the browser window
locator: returns a record of class cLocator (new).
container file: this is now obsolete; it is deprecated and will disappear soon (replaced by "locator")
usage: this is now an enumeration
properties: (on "get":) a record of the most important properties of the fragment

properties of import libraries:

container: the fragment
weakly linked: added support for modifying this attribute from AppleScript

properties of symbols:

container: either the fragment (exports) or library (imports)
weakly linked: added support for modifying this attribute from AppleScript

select <reference> -- previously supported windows only, now supports fragments/libraries/symbols as well
find library <name> -- new (same as the Find Library command)
open context -- now returns an error when the context cannot be found

Bugs Fixed in version 1.1

Fixed a conflict with Action Files (thanks to the author, Brian Zuk)
Open Context no longer opens multiple browsers for the same context
Improved error-reporting when a plug-in file cannot be found at load time
Fixed a couple bugs with scanning for plug-ins
Worked around an obscure "feature" of the Code Fragment Manager: CFM (rather, the Process Manager) initially loads application fragments using the application file name instead of the application fragment name. If, down the line, another fragment is loaded that links to the application fragment (that is, imports symbols exported by the application), CFM *renames the application fragment on the fly*! Stop the insanity! Fragmalyzer now detects this bit of nastiness when it occurs and updates the name of the application fragment in the browser.
Context browsers properly reflect fragment UNloading now
C++ unmangler: the Fragmalyzer now uses the standard Apple C++ unmangler, and no longer attempts to undecorate MSVC C++ symbols.
A number of other fixes.